Virtual subscriber identity module

ABSTRACT

A mobile trusted platform (MTP) configured to provide virtual subscriber identify module (vSIM) services is disclosed. In one embodiment, the MTP includes: a device manufacturer-trusted subsystem (TSS-DM) configured to store and provide credentials related to a manufacturer of the MTP; a mobile network operator-trusted subsystem (MNO-TSS) configured to store and provide credentials related to a mobile network operator (MNO); and a device user/owner-trusted subsystem (TSS-DO/TSS-U) configured to store and provide credentials related to user of the MTP. The TSS-MNO includes a vSIM core services unit, configured to store, provide and process credential information relating to the MNO. The TSS-DO/TSS-U includes a vSIM management unit, configured to store, provide and process credential information relating to the user/owner of the MTP. The TSS-DO/TSS-U and the TSS-MNO communicate through a trusted vSIM service.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation in part of U.S. patent application Ser. No. 12/168,791 filed Jul. 7, 2008 which claims the benefit of German Patent Application No. 102007044905.6 filed Sep. 19, 2007.

FIELD OF INVENTION

This application is related to wireless communications.

BACKGROUND

With the growing number of wireless communication devices, there is a need to provide a more dynamic solution to the current subscriber identity module (SIM) function carried out within a SIM card or UICC, to overcome some specific shortcomings in relation to modern and evolving mobile communication networks. The UICC provides a secure execution and storage environment from which to execute the SIM authentication algorithms and store credentials. However, the cost of the UICCs, their impractical form factor, and limited functionality prevent them from being used in applications where the mobile network operator may only be known some time after the purchase of the wireless device. Alternatively, the UICC fails when multiple operator networks are to be supported or accessed simultaneously within one device. Methods to update or change mobile network and service subscriptions are limited with SIM cards, and are generally lacking, when over-the-air deployment is desirable.

Furthermore, though the SIM card or UICC is generally considered to be highly secure, this security is not linked strongly to security properties of the whole device on which it resides. This limits the application of scaling security concepts for advanced services and applications such as mobile financial transactions. All of these problems are imminent for autonomous devices connected to mobile networks for instance in machine-to-machine (M2M) communication scenarios.

Accordingly, a more dynamic and concurrently secure software based solution to the SIM function is needed.

SUMMARY

A mobile trusted platform (MTP) configured to provide virtual subscriber identify module (vSIM) services is disclosed. In one embodiment the MTP includes: a device manufacturer-trusted subsystem (TSS-DM) configured to store and provide credentials related to a manufacture of the MTP; a mobile network operator-trusted subsystem (TSS-MNO) configured to store and provide credentials related to a mobile network operator (MNO); and a device owner/user-trusted subsystem (TSS-DO/TSS-U) configured to store and provide credentials related to user of the MTP. The TSS-MNO includes a vSIM core services unit, configured to store, provide and process credential information relating to the MNO. The TSS-DO/TSS-U includes a vSIM management unit, configured to store, provide and process credential information relating to the user of the MTP. The TSS-DO/TSS-U and the TSS-MNO communicate through a trusted vSIM service. Optionally, the MTP may separate the device user and device owner function into a TSS-DO and TSS-U and may include a second TSS-U configured to store and provide credentials relating to a second user of the MTP. Also, the MTP may include a device owner-trusted subsystem (TSS-DO) configured to store and provide credentials related to an owner of the MTP. The MTP may also include a second MNO-TSS configured to store and provide credentials related to a second MNO.

Also disclosed is a procedure for remotely creating a trusted subsystem for use in providing vSIM services.

Also disclosed is a procedure for registering and enrolling a trusted subsystem for use in providing vSIM services.

Also disclosed is a procedure for delivering a trusted subsystem for use in providing vSIM services from a remote location to an MTP.

Also disclosed is a procedure for migrating a trusted subsystem for use in providing vSIM services from a source MTP to a target MTP.

Also disclosed are three related methods for allowing a subscriber using a vSIM configuration to access a wireless network.

BRIEF DESCRIPTION OF THE DRAWINGS

A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings wherein:

FIG. 1 shows an example of a communication system architecture configured to use services and determine subscriber identity using a software based virtual subscriber identity module (vSIM);

FIG. 2 shows an example of a vSIM architecture for a single user mobile trusted platform;

FIG. 3 shows an example of a vSIM architecture 300 for a multi user mobile trusted platform;

FIG. 4 shows a procedure for installing a TSS-MNO on a pristine mobile trusted platform;

FIG. 5 shows a procedure for subscriber registration and delivery of the vSIM credential;

FIG. 6 shows an example of a procedure for the second phase of secure delivery and installation of the subscriber-related portion of the vSIM credential;

FIG. 7 shows an example of a procedure for migrating vSIM credential or its execution environment from a source platform to target platform;

FIG. 8 shows an example of a communication system configured to perform a first procedure for allowing access of a communication subscriber;

FIG. 9 show an example of a communication system configured to perform a second procedure for allowing access of a communication subscriber;

FIG. 10 show another example of a communication system configured to perform a second procedure for allowing access of a communication subscriber; and

FIG. 11 shows a third procedure for allowing access of a communication subscriber for a general network infrastructure.

DETAILED DESCRIPTION

When referred to hereafter, the terminology “wireless transmit/receive unit (WTRU)” includes but is not limited to a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular telephone, a personal digital assistant (PDA), a computer, a mobile trusted platform, or any other type of user device capable of operating in a wireless environment. When referred to hereafter, the terminology “base station” includes but is not limited to a Node-B, a site controller, an access point (AP), or any other type of interfacing device capable of operating in a wireless environment. The term “trustworthiness” is regarded as a standard which describes the status of an application and/or service. This status signifies that an application and/or service can directly or indirectly provide an indication of its integrity and correct functioning.

FIG. 1 shows an example of a communication system architecture configured to use services and determine subscriber identity using a software based virtual subscriber identity module (vSIM). The communication system 100 includes a user or device owner (DO) 110, a trusted mobile platform 120, a base station 130, a network service provider (MNO) 140, and point of sale (POS) 150. The DO 110 communicates with the POS for the purpose of registration and enrolment 155 with the POS 150. The POS 150 communicates with the MNO 140 in order to perform subscriber registration 160. The MNO 140 communicates with the trusted mobile platform to deliver the vSIM credential 165. The DO 110 provides information to the trusted mobile platform 120 in order to authenticate 170 the user. The trusted mobile platform then sends the subscriber authentication 175 to the base station 130. The base station 130 then communicates with the MNO 140 to verify the user authentication information.

In general the vSIM architecture of FIG. 1 is protected by a trusted operating system which is based on a permanently assigned trusted anchor and which supports multiple separate and trusted execution environments or sub systems. As shown, one execution environment is assigned to a specific stakeholder, and additional stakeholders beyond those pictured would be possible.

The architecture shown in FIG. 1 takes four important entities into account. In this scenario, the DO/U intends to establish a long-term relationship with the MNO in order to use a mobile communications network and the services offered therein (for example, GSM, UMTS telephone, data services, or specialized location-based services).

Instead of using a physically present SIM card, the MNO provides the MTP with a software-based access authorization credential or vSIM credential. The vSIM credential is composed of a subscriber-related portion and a user-related portion. Every time that a registered device user must be initially authorized by the communications network, they are first authenticated for the vSIM service via the user-related portion of the vSIM credential. In the course of the communication relationship, this service uses the subscriber-related portion of the vSIM credential for network authentication.

FIG. 2 shows an example of a vSIM architecture for a single user mobile trusted platform (MTP) 200. The mobile trusted platform 200 includes three separate trusted sub systems (TSSs) 202, 204, 206. The first TSS 202 is allocated to the device manufacturer (DM). The second TSS 204 is allocated to the network service provider (MNO). The third trusted TSS 206 is allocated to the DO 206. It should be noted that TSS-DO may also be allocated to the user (TSS-U). Each of the three TSSs 202, 204, 206 includes a normal services unit 210 a, 210 b, 210 c, a trusted services unit 212 a, 212 b, 212 c, and a trusted resources unit 214 a, 214 b, 214 c. The MNO trusted TSS 204 also includes a vSIM core unit 220, for performing the SIM functions related to the MNO. The DO trusted TSS 206 also includes a vSIM management unit 222 for performing the SIM functions related to the DO. The vSIM core unit 220 and the vSIM management unit 222 communicate through a trusted link 224 and combine to perform at least the functions of a conventional universal subscriber identity module (USIM).

FIG. 3 shows an example of a vSIM architecture 300 for a multi user MTP 300. The mobile trusted platform 300 includes four separate TSSs 302, 304, 306 and 308. The first TSS 302 is allocated to the device manufacturer (DM). The second trusted TSS 304 is allocated to the network service provider. The third TSS 306 is allocated to a first user. The fourth TSS 308 is allocated to the device owner 308. Each of the four TSSs 302, 304, 306 and 308 includes a normal services unit 310 a, 310 b, 310 c, 310 d, a trusted services unit 312 a, 312 b, 312 c, and a resources unit 314 a, 314 b, 314 c. The MNO TSS 304 also includes a vSIM core unit 320, for performing the SIM functions related to the MNO. The user TSS 306/308 also includes a vSIM subscriber management service 322/323 that performs functions pertaining administration and authentication of local users. More specifically this service provides an authentication oracle to the vSIM core service 320 such that evidence is given as to a local user's identity. The vSIM core unit 320 and the vSIM management unit 322 communicate through a trusted link 324 and combine to perform at least the functions of a conventional universal subscriber identity module (USIM).

In general, MTPs 200 and 300 support multiple protected, separate execution environments. Each environment represents an area associated with a stakeholder. The MTPs 200 and 300 are configured to implement a vSIM service which replaces the conventional smart card-based SIM card and its function. In general, the vSIM service extends to (at least) three different execution environments as is shown in FIG. 2, however, it maybe extended to support numerous other execution environments, which is shown by example in FIG. 3.

As shown in FIGS. 2 and 3, several different stakeholders (sigma) are considered: the device manufacturer (DM), the network access and service provider (mobile network operator, MNO), the device owner (DO), and the user (U). A trusted subsystem TSS-sigma is configured as a logical unit comprising the trusted execution environment (TE-sigma) and the non-exchangeable security module (trusted module, TM) or the entity of the security module (TM-sigma) associated with the remote owner (RO) or stakeholder (sigma). A TSS-sigma is always configured to sign and encrypt any given data. A TSS-sigma has access to a trusted service RTV-sigma. This service is responsible for verification, for example of defined system states based on reference data. Various other trusted subsystems of a similar architecture proposed herein are described below by way of example. These include the subsystems TSS-DM 202 & 302, TSS-MNO 204 & 304, TSS-DO 206 & 306, and TSS-U 206 & 308 of stakeholders DM, MNO, DO, and U.

The TSS-DM 202 & 302 is responsible for the integrity, configuration, and installation of the device together with its installed hardware components. It provides all security-sensitive resources for a device. The TSS-DM 202 & 302 generally controls all internal and external communications and secures the communications channel. Consequently, all protocol messages of a TSS-sigma are transmitted by the communications services of the TSS-DM 202 & 302 for the destination point thereof.

All subscription-dependent and subscriber-related network provider services of a platform are allocated to the TSS-MNO 204 & 304. This subsystem is responsible for managing and protecting the subscriber-related portion of the vSIM credential, and performs the client-side network authentication of a subscriber. The subsystem provides the vSIM core service (vSIM-CORE) for this purpose. The vSIM-CORE 220 & 320 is configured to substitute essential functions (subscriber authentication) for the conventional SIM, but may also accommodate other authentication features. The term “trusted subsystem TSS-MNO” is synonymous with a fully equipped TSS-MNO which provides the necessary vSIM-CORE service 220 & 320. A combination of TSS-DM and TSS-MNO is also possible. It should also be noted that the vSIM core service is responsible for the secure storage and use of subscriber data as well as the subscriber authentication with the MNO.

The TSS-U 206 & 306 protects all user-related and private information, in particular the user's associated access authorization credential (user-related portion of the vSIM credential). The TSS-U 206 & 306 instantiates the vSIM management service (vSIM-MGMT) 222. This service is responsible for management of user information and for computation of authentication responses for the local user. The service vSIM-MGMT provides the service vSIM-CORE with an internal authentication oracle. vSIM-MGMT is thus able to provide proof of identity of the local user after authentication inquiries. This service is responsible for the user management of a vSIM, in particular for the administration and management of a device user. The owner management service vSIM-OwnMGMT in vSIM is functionally imaged in vSIM-MGMT. It should also be noted that any TSS-U is able to generate suitable cryptographic keys which may be accessed and used only by the intended platform user U for a digital signature.

The TSS-DO 206 & 308 instantiates the vSIM owner management service (vSIM-OwnMgmt). This service is responsible for managing owner information and for administrative management, such as for local users or service providers. TSS-DO and TSS-U may also be combined into one for single-user systems as shown in FIG. 2.

The MTP in general, is a mobile platform having a non-exchangeable security module (trusted module, TM) permanently associated with the hardware platform. In the context of the vSIM architecture under consideration, the MTP is not mandatorly provided with a conventional security token for subscriber authentication such as a conventional SIM card. The MTP operates a trusted operating system. The trusted software layer supports multiple separate trusted subsystems (TSS_SIGMA) with a protected and insulated execution and memory function.

Each trusted subsystem (TSS_SIGMA) is used for critical security functions for a stakeholder. The trusted subsystem is composed of a trusted entity of the security module (TM-SIGMA) and an associated trusted execution environment (trusted engine, TE_SIGMA), and trusted services (TS_SIGMA). At least the three trusted subsystems TSS-DM, TSS-MNO, TSS-U on behalf of the remote owners DM, MNO, U exist on an MTP. The procedures are described for a single-user system. The device owner DO and the function of the TSS-DO are imaged for U or TSS-U.

It should be noted that, the MNO directly or indirectly provides the necessary functions of a public key infrastructure. The MNO possesses a certificate Cert-MNO which has been issued by a certification authority CA. This certificate links the identity of the MNO to the public key K-pub-MNO, which is necessary for checking digital signatures. This certificate is available to the MTP and all embedded services.

It is noted that the procedures described below consider a single-user system for purposes of example only. As a result, the device owner DO is made equivalent to the user U. As shown in FIG. 3, the methods for subscriber authentication in multiple-user systems with separate TSS-DO and TSS-U, are carried out in an analogous manner, and would be within the scope of this application. Other multi-user scenarios are possible, for example: (1) one TSS-U and multiple TSS-MNOs; (2) one TSS-MNO and multiple TSS-Us; and (3) multiple TSS-Us and multiple TSS-MNOs. To avoid the circumvention of ownership control, only one DO is permissible in any such configuration. In the various multi-user scenarios the vSIM-MGMT service, as it applies to the DO only, is configured to straddle and be compatible with all users as well as multiple vSIM-CORE service manifestations. Hence for a single user, the vSIM-MGMT service is separated into a vSIM-MGMT-DO and vSIM-MGMT-U function. This is advantageous in application scenarios where for instance a group of users (e.g., a family) would use the same MNO subscription, or, on the other hand, when a single user would want to choose from more than one MNO subscription depending on circumstances, for instance when being abroad. The preferred method to implement them is that either vSIM-CORE and/or vSIM-MGMT hold secured databases including authorization secrets of the respective other services in the respective other TSS to establish the desired 1 to n, n to 1, or n to m relationship between the respective TSS and between the various vSIM-MGMT and vSIM-OwnMgmt.

The proposed vSIM architectures of FIGS. 2 and 3 assume security characteristics that are equivalent to conventional architectures for subscriber authentication based on conventional security tokens. In particular, these architectures assume the protected storage function, a separate tamper-protected execution environment, and authentication of a user. A vSIM platform must also ensure that only authorized subjects are able to access or manipulate protected data of the vSIM credential. This is particularly important while this data is: in transit to the vSIM execution environment or to other trusted services; stored in the volatile or nonvolatile memory of the MTP; executed or used within the execution environment; or transferred between various trusted environments by authorized subjects. This includes the feature of an attacker that is not able to destroy or modify security-sensitive data, or circumvent the access control mechanisms. The system must also prevent loss and escape of security-sensitive data, and ensure that all necessary services are available and functional. In particular, the vSIM architecture must ensure that authorized subjects are able to access security-sensitive services only through appropriate (local or remote) owners.

FIG. 4 shows a procedure 400 for installing a MNO-TSS 406 on a pristine mobile trusted platform 403 having a TSS for the device manufacturer (TSS-DM) 404 and TSS for the user (TSS-U) 402 in communication with an MNO 408. It should be noted that the term TSS-MNO is used to refer to both the trusted subsystem established by this procedure and also the trusted execution environment (TE) MNO (TE-MNO) which will become the TSS-MNO at the end of the procedure. The taking of possession by a remote owner (RO) establishes the fundamental and elementary relationship of trust between the remote owner or stakeholder and the MTP. The procedure requires that an empty or pristine execution environment exists. The first part of the procedure 410 is dedicated to preparing the empty execution environment, while the second part 412 is dedicated to remotely taking ownership of the newly created trusted engine (TE). The pristine TSS-MNO (TSS*-MNO) is composed of a pristine standard execution environment (TE*-MNO) having a base functionality and/or a number of trusted services. When the subsystem TSS*-MNO is able to provide the MNO with proof of its untouched configuration, structure, and conformity regarding its security policy, it is certified by the MNO.

The preparation part 410 of the procedure 400 begins when the TSS-U 402 sends a request to establish a TSS-MNO to the TSS-DM 404 at 420. The TSS-DM 404 then installs an original execution environment at 422. Then the TSS-DM 404 sends the initial set up sequence to the newly created TE*-MNO, at 424. An “empty” execution environment TE*-MNO is established, and a new entity of the security module TM-MNO 406 is activated or created, at 426. In addition, a pristine execution environment TE*-MNO is established and prepared. In particular, an endorsement key pair EK*-TSS-MNO together with a corresponding endorsement certificate Cert-TSS-MNO is created within the TE*MNO. The TSS-MNO 406 sends a status message back to the TSS-DM 404, at 428.

The remote take ownership part 412 of the procedure 400 begins when the TSS-DM 404 sends a request for taking possession by remote owner (MNO) message to the MNO 408, at 430. The MNO 408 then performs verification of the trusted mobile platform 401 and the execution environment TS-MNO 406, at 432. Next the MNO 408 sends a status message to the TSS-DM 404 at 434. Next, the TSS-DM 404 sends a certificate CERT_MNO and additional information to the MNO 408, at 436. Then the MNO 408 checks and signs the certificate CERT_MNO and sets up a configuration and security policy, at 438. The MNO 408 sends a status message to the TSS-DM 404, at 440. Then the TSS-DM 404 sends a completion of execution environment TSS-MNO 406 to the TSS-MNO 406. Next, the TSS-MNO completes the initial set up by installing the CERT_MNO and performing a final set up and installation procedure, at 444. Then the TSS-MNO 406 sends a status message back to the TSS-DM 404, at 446. The TSS-DM 404 forwards a status message along to the TSS-DO 402, at 448. The TSS-DM 404 also sends a status message to the MNO 408, at 450.

While FIG. 4 describes a specific implementation of a remote take ownership procedure, the following description describes a more general procedure with a similar end point as the procedure in FIG. 4. A device owner (DO) of an MTP must be able to purchase an “empty” communications terminal, such as a mobile telephone, that has not been pre-allocated and initialized by a specific MNO so that the user U or the device owner DO may freely choose any given MNO without restrictions. The procedure of FIG. 4 is used to perform the taking possession of the TSS-MNO by a remote owner and to complete establishment of the vSIM execution environment by the MNO. It should be noted that the method may be directly transferred to any given remote owner, and is not restricted to the MNO.

The TE*-MNO then attests its current status. The attestation may be performed by the local verifier RTV-DM of the TSS-DM, using reference values (RIM) and corresponding certificates of the remote owner MNO. Note that the RIM corresponding to TE*-MNO (a trusted engine in a pristine state) may not necessarily be associated with a particular MNO and may have no more configuration beyond an initial base functionality. If no matching RIM and/or corresponding RIM certificate is available for the execution environment, the attestation may be performed using an external (accepted) verification entity. The attestation ATTEST(S_(i)) is signed by the RTV signing identity (RTVAI).

TE*_(MNO)→MNO:ATTEST(S _(i))  (Equation 1)

The TE*-MNO generates a symmetrical session key Ks and uses it to encrypt the public portion of the endorsement key EK*-TSS-MNO, the corresponding certificate Cert-TSS*-MNO, the attestation data, and information about the intended purpose. The TE*-MNO then encrypts the session key Ks together with the public key K-pub-MNO and sends both messages to the MNO. Without loss of generality, the TE*-MNO may use an attestation identity key AIK*-TSS-MNO instead of the endorsement key EK*-TSS-MNO and a corresponding certificate Cert-TSS*-MNO, certification data, and information about the intended purpose.

It is assumed that this key K-pub-MNO is either publicly available or is preinstalled by the device manufacturer.

TE*_(MNO):ENK_(Ks)({EK*_(MNO),Cert*_(TSS) _(MNO) , . . . }),ENC_(MNO)(K _(S))  (Equation 2)

The attestation (equation 1) and the EK*-TSS-MNO and its certificate as well as the session key Ks that encrypts it (equation 2) may be transmitted separately but in the same session (i.e. bounded by the same session nonce). Alternatively, the transmission could be done at once, using the same session key Ks, hence in this case:

TE*_(MNO)→MNO:ENK_(Ks)({EK*_(MNO),Cert*_(TSS) _(MNO) , . . . },ATTEST(S _(i))),ENC_(MNO)(K _(S))  (Equation 3)

After the MNO has received the messages, they are decrypted using the private portion of the asymmetrical key K-pub-MNO.

In the subsequent step the MNO verifies the certification data and checks the intended purpose of the TSS*-MNO. If the data for the execution environment and the device certification are valid and the intended purpose is accepted, the MNO produces an individual security policy SP-MNO. The MNO signs the Cert-TSS-MNO and generates RIM values and RIM certificates for a “complete” TSS-MNO, which is configured to operate with a particular service provider. These are necessary for local verification of the TSS-MNO.

The MNO also generates an initial configuration SC-TSS-MNO. This is used to individualize the execution environment or to complete same with regard to the intended purpose and the particular security policy. The individualization generally includes software not initially present to enable appropriate functionality. The RIM and RIM certificate are generated to reflect this initial configuration. In the next step the MNO encrypts the messages using the public portion of the key (EK-pub-TSS-MNO), and transmits this packet to the TE*-MNO, which can in particular be performed via the base network connection provided by TSS-DM. Note that SP-TSS-MNO and SC-TSS-MNO are MNO-specific and the TSS-MNO's expected ‘post-completion’ state that corresponds to the SP-TSS-MNO and SC-TSS-MNO needs to be defined by a new RIM certificate.

MNO→TSS_(MNO):ENC_(TSS) _(MNO) ({SP_(MNO),SIGN_(MNO)(Cert_(TSS) _(MNO) ),RIM_(TSS-MINO),SC_(TSS) _(MNO) })  (Equation 4)

The execution environment TE*-MNO decrypts the received packet and installs it within the TSS-MNO. Lastly, the establishment is completed based on the configuration SC-TSS-MNO. This means in particular that all services not yet installed and which are required by the SC-TSS-MNO are introduced or installed in the TSS-MNO.

The procedure for subscriber registration and delivery of the vSIM credential is shown in FIG. 5, and described below. To make use of the vSIM service, an access authorization credential (vSIM credential) must be available to the MTP 200. This vSIM credential is either (1) generated by the MNO 506 and installed by the MNO or DM beforehand, (2) is based on initially secret information, used to install the vSIM credential or (3) is generated (by the MNO 506 and the user U 502) during the take ownership process.

Since the services of the vSIM architecture are implemented as trusted software applications, the respective subscriber-related portion of the vSIM credential must be securely transmitted by the MNO to the vSIM service. In conventional SIM-based systems the subscriber receives a security token (smart card/SIM card) directly after being registered. In contrast to the vSIM credential, this security token physically exists and is delivered with a pre-installed key or SIM credential for the respective POS.

In a preparatory phase (not shown) the MTP 200 has executed a certified initial startup procedure and has loaded a specific trusted software layer of the OS and its trusted units. This includes the trusted execution environments together with their embedded services vSIM-CORE and vSIM-MGMT. The trustworthiness of the platform has been checked, and the installed hardware and running software are in a trusted, acceptable, and plausible status and configuration. The platform is thus in a state that is described as ‘having achieved a secure boot’ with a vSIM function installed. Additionally, upon request, the platform is also able to report this status through an authorized entity and to certify the status.

The POS 504 orders any given number of previously generated registration tickets Ticket-i from the MNO 506.

POS→MNO: Ticket Request (i.e. order)  (Equation 5)

IMSI-i stands for an international mobile subscriber identity. Alternatively, this may be a random, unambiguous identifier (ID) that is assigned by the authorized center or an ID that signifies the ID of a service subscriber for whom the service is provided through the communication network. In case IMSI-i is an IMSI, such tickets can be distinguished by their unique indices.

The term RAND-i stands for a random value. This value is necessary for checking the identity of the TSS-MNO 204 during the protocol. By use of AUTH-i the MTP 200 is able to check the integrity and authenticity of the ticket-i. AUTH-i is a signature of the MNO 506 signed by a private key of the MNO 506. By decrypting AUTH-i the POS 504 can identify the MNO 506 that originated the Ticket-i. The authentication of the POS 504 by the MNO 506 is not considered in the protocols described herein but it is considered sufficiently trustworthy to take possession of and dispense tickets. The MNO 506 sends a number of tickets to the POS 504. A registration ticket is composed of the triplet {IMSIi, RANDi, AUTHi}:

MNO→POS: Ticket_(i):={IMSI_(i),RAND_(i),AUTH_(i)}  (Equation 5b)

If multiple pristine trusted subsystems (TE*-MNOs) with their own roots of trust are installed by the DM it is then possible for the MNO 506 to take ownership of these subsystems separately and thereby regard each as a distinct device. In this scenario multiple users can register via these separate subsystems on a one-to-one basis.

It should also be noted that the registration procedure described in FIG. 4 is distinct from the registration procedure of FIG. 5, as well as subsequent protocols described in this patent application. Therefore the procedure of FIG. 5 does not require the use of a particular take-ownership procedure.

The user registration and the vSIM credential roll-out procedure are separated into two phases. The following procedure is illustrated in FIG. 5, and describes the first phase. The user registration and registration for subscriber-related services of the MNO 506 are specified in the first phase.

The user starts the protocol by requesting a new identity credential (user-related portion of the vSIM credential) for a local user for the TSS-U/DO 206, which is generated by same. For this purpose the local user submits a unique identity code ID-U, his personal registration data REGDATA-U, and a secret authorization password CHV-U to the trusted service vSIM-MGMT at 550. The use of the unique ID-U eliminates the possibility that the same user (U) 502 can use different ID-U's to register the same platform to the same MNO 506 for vSIM user registration purposes. The information shown in Equation 6 originates at the POS 504, some of which is generated by the user 502 (probably REGDATA-U and CHV-U) and some (ID-U) by the POS 504 itself.

U→vSIM_(MGMT): ID_(U),CHV_(U),REGDATA_(U)  (Equation 6)

vSIM-MGMT then generates an asymmetrical signature key pair K-U and generates a corresponding certificate which includes all of the user's relevant information (REGDATA-U, the public portion of K-U), at 552. The service vSIM-MGMT then transmits the certificate CERT-U and an attestation, signed by the private portion of K-U, to the service vSIM-ECORE, at 554. Within the scope of a trusted environment it is assumed that a secure link is established between the vSIM-MGMT and vSIM-CORE.

vSIM_(MGMT) →vSIM_(CORE):ATTEST(S _(i)),CERT_(U)  (Equation 7)

At this point, the service vSIM-MGMT initiates a registration procedure and certifies its current status and configuration to the local verifier (RTV-MNO) of the services vSIM-CORE. The TSS-MNO 204 checks the provided data based on the reference data. The TSS-MNO 204 then checks whether the status of the current execution environments is in a valid and acceptable state. The certified asymmetric key pair K-U serves as means by which the attestation of the current execution environment is verified, at step 556. As soon as the vSIM-CORE determines the reliability of the device, it generates an unique identifier PID and sends this value to the vSIM-MGMT 558.

vSIM_(CORE)→vSIM_(MGMT):PID  (Equation 8)

The user transmits the registration data REGDATA-U (for example, name, address, accounting information, personal identification number) and the PID to the POS over what is considered to be a secure channel, where encryption is performed if necessary, at 560. The service vSIM-CORE initiates a registration procedure for the user U 502. For this purpose vSIM-CORE signs its own certificate and the received user certificate. vSIM-CORE then sends this packet to the POS 504.

U→POS: PID,REGDATA_(U)  (Equation 9a)

vSIM_(CORE)→POS:CERT_(TSS) _(—) _(MNO),CERT_(U)  (Equation 9b)

vSIM_(CORE)→POS:SIGN_(TSS) _(MNO) (PID,CERT_(TSS) _(—) _(MNO),CERT_(U))  (Equation 9c)

After the POS 504 has received the request, it selects a ticket-i, binds it to the key K-pub-TSS-MNO 204, at 564 and sends it back to the TSS-MNO 204, at 566. The PID provides a handle by which the user is uniquely identified with the ticket. Also, the POS 504 is able to use the PID to associate the user with the registration request being made by the vSIM-CORE. In this case the POS 504 may be any given point of sale accredited by the MNO, such as an Internet portal.

POS-TSS_(MNO):BIND_(TSS) _(MNO) (Ticket_(i))  (Equation 10)

As soon as the POS 504 has determined the trustworthiness of the user U as well as the device, it adds the CERT-U and the IMSI-i (of the selected ticket) to REGDATA-U. The POS 504 then signs the collected information with the private portion of its signature key K-POS and sends the signed data and the signature (online or offline) to the MNO 568. The POS 504 optionally encrypts the data, using the public portion of the K-MNO.

POS-MNO:IMSI_(i),CERT_(U),REGDATA_(U)

:SIGN_(POS)(IMSI_(i),CERT_(U),REGDATA_(U))  (Equation 11)

The MNO 506 checks the data and generates the subscriber-related portion of the vSIM credential using IMSI-i, the symmetrical key Ki, and the certificate CERT-U. The MNO 506 then signs this bundle with the private signature key K-MNO, and lastly, activates the signed vSIM credential and the respective NONCES in its authentication center, at 570.

The MTP 200 can then request an available registration service of the MNO 506 via an existing communication channel. This service may be implemented, for example, as a network telecommunications service or Internet service.

A variant (not pictured) of the registration process above and depicted in FIG. 5 includes an authentication and possible attestation of the POS. It mitigates the following threat to MNOs and Users: A rogue POS may collude with other, possibly fake, POS. It may distribute multiple copies of tickets received from MNO to other POS and distribute them to many devices and users and charge them for this. Though the MNO can trace back this kind of fraud to the originating POS, the attack may still succeed in some distributed scenarios such as POS in different countries. To prevent this, the TSS_MNO needs to obtain information certifying the trustworthiness of the POS.

The aforementioned threat can be mitigated as follows. At the time of the ordering of the registration tickets (equation 5), the POS also performs a remote attestation toward the MNO by sending attestation data ATTEST_POS, as specified by the remote attestation protocol of the Trusted Computing Group, in the same or a separate message, signed by the POS. The ticket request or order message from the POS to the MNO should now include POS attestation data.

POS→MNO:Ticket Request,ATTEST_POS  (Equation 5c)

It should be noted that the MNO should have obtained, from a trusted third party, the decryption key for the signing key that the POS used to sign its attestation data and a certificate for the key. Ticket ordering and attestation message must in any case be bound into one session for instance by a common nonce to prevent replay attacks. The MNO then knows that the ticket order originates from a known POS in a trustworthy state. This requires that the POS keeps tickets in protected memory locations not accessible to unauthorized parties within or outside the POS infrastructure. The tickets submitted to the POS are augmented by the MNO with POS signing keys Tr-POS and digital certificates CERT-Tr-POS indicating the trust state for this set of keys. The keys is then used by the POS to sign messages to TSS-MNO 566, as in Equation 10.

To further increase trust levels between TSS-MNO and POS, a message exchange may be included in the ticket request 560, before sending the registration data (Equation 9a-c). That is upon receiving an initial message from TSS-MNO, containing the public part of TSS-MNO's encryption key, indicating a ticket request, the POS sends a message signed with Tr-POS, containing Cert-Tr-POS and optionally an encryption key, encrypted with the public part of TSS-MNO's encryption key, to establish a secure channel for the subsequent communication. TSS-MNO extracts the Tr-POS public key from Cert-Tr-POS and verifies the signature of this data packet with it. TSS-MNO then verifies the MNO signature of Cert-Tr-POS. The TSS-MNO then knows that the response to the initial ticket request originates from a POS whose trustworthiness is certified by the MNO. TSS-MNO then optionally decrypts the encryption key, if present. All subsequent communication between POS and device is secured with this key. The TSS-MNO can compare the certificates of received tickets 566 with the one received in the ticket request initial exchange to ensure that he receives tickets which were obtained by the POS in the trustworthy state signified by Cert-Tr-POS.

In another embodiment, the POS has not been previously proven to be trustworthy. Moreover, the POS cannot attest itself to the MNO. Therefore, the trustworthiness of the POS is not guaranteed. This embodiment relies on establishment of a certified asymmetric key pair between the user platform and the MNO. Such a key pair may be established during the remote take-ownership protocol. Once established, it provides a mechanism by which any reliance on the trustworthiness of the POS to handle critical data is reduced. With this security configuration change the MNO sends the ticket to the POS encrypted with the public key of the TSS-MNO and signed using the private portion of K-MNO.

Given that only the TSS-MNO with the required private key can decrypt the message, a multi-MNO scenario managed by the POS is employed. The key certificate of the TSS-MNO allows the POS to make the association with the MNO that sent the tickets for a given user. The POS may also make associations in this way with respect to more than one MNO, thus guaranteeing that the TSS-MNO receiving the ticket can decrypt it. It should be noted that a message for binding the ticket information may be embedded in this process.

Assuming a successful registration, the TSS-MNO extracts the IMSI from the decrypted ticket, encrypts it with the public key of the MNO (key pair established above), signs it with K-priv-TSS-MNO and sends this message to the POS. After signature verification the POS passes the encrypted IMSI along with the user certificate and registration data to the associated MNO. The final roll out of the credentials is performed in essentially the same way as shown below in equations 16 and 17.

The confidentiality of the ticket information is protected from a potentially malicious POS. The ticket can neither be misused against the user platform nor the MNO. Nor can it be redirected to, for example, a miscreant user or POS. Other information, including REGDATA_(U), and CERT_(U), is accessible by the POS and thus subject to a possible spoofing attack. However, this information is integrity protected and so such an attack is prevented.

FIG. 6 shows an example of a procedure for the second phase of secure delivery and installation of the subscriber-related portion of the vSIM credential (according to the non-variant basic model) onto the mobile trusted platform 200 of FIG. 2. To obtain the subscriber-related portion of the vSIM credential, the user applies to the registration service of the MNO 604. For this purpose the user U 602 submits his ID-U and the associated password CHV-U to the service vSIM-MGMT. vSIM-MGMT then loads the associated key pair Ku (user-related portion of the vSIM credential) from the protected memory, at 650.

U→vSIM_(MGMT):ID_(U),CHV_(U)  (Equation 12)

Subsequently, the vSIM-MGMT initializes a rollout procedure, and for this purpose sends a request to vSIM-CORE, at 652.

vSIM_(MGMT)→vSIM_(CORE):init_rollout_(vsim)  (Equation 13)

After the request message is received, the vSIM-CORE releases the respective ticket_(i) and checks the authenticity and integrity of the ticket-i, at 654. vSIM-CORE then extracts the value NONCE-U from the ticket-i and requests U 602 to verify his identity via the vSIM-MGMT.

vSiM_(CORE)→vSIM_(MGMT):NONCE_(U)  (Equation 14)

The service vSIM-MGMT signs the NONCE-U together with ID-U and REGDATA_(U). This bundle is sent back to vSIM-CORE, at 655.

vSIM_(MGMT) →vSIM_(CORE):SIGN_(TSS) _(U) (REGDATA_(U),ID_(U)∥NONCE_(U))  (Equation 15)

As soon as the service vSIM-CORE has received the message, it generates a vSIM credential delivery request and submits same to the assigned registration service of the MNO 656. For this purpose the service vSIM-CORE extracts the NONCE-MNO from the ticket-i and signs it together with IMSI-i. vSIM-CORE then sends its generated signature and the received user signature, via some quarantine channel or the internet, to the MNO 656.

vSIM_(CORE)→MNO:SIGN_(TSS) _(MNO) (IMSI_(i)∥NONCE_(MNO))SIGN_(TSS) _(U) (REGDATA_(U),ID_(U)∥NONCE_(U))  (Equation 16)

After the request from the vSIM CORE is received, the MNO 604 checks the messages, the CERT-U, and the Cert-TSS-MNO (with verification either based on the received data or from the local memory or a certificate provided by the POS (not in picture)), at 658. If the information is invalid or is rejected, the MNO 604 replies with an error message and terminates the protocol. The NONCE_(MNO) and NONCE_(U), both extracted from the ticket, are challenges to the MNO 604 and U 602 respectively. The REGDATA_(U) is sent to enable correlation with ID_(U). They are not used for freshness, instead, freshness can be achieved in various ways, for instance by adding timestamps of suitable granularity in the messages.

In another scenario, the request is approved by the MNO 604. The MNO then prepares the subscriber-related portion of the vSIM credential for transmission to the vSIM-CORE. The MNO 604 generates a randomly selected session key Ks. The key Ks together with the corresponding key from the TSS-MNO 204 are then linked to the target platform, at 660, so that the data (in this case, the key Ks) may be used only by an associated authorized entity. The MNO 604 encrypts the subscriber-related portion of the vSIM credential together with the session key, and sends both to the TSS-MNO 204, at 662.

MNO→vSIM_(CORE):ENC_(K) _(S) (Cred_(vSIM)∥SIGN_(MNO)(Cred_(vSIM)))  (Equation 17a)

BIND_(TSS) _(MNO) (K_(S))  (Equation 17b)

Lastly, the TSS-MNO 204 releases the session key Ks. With this key the TSS-MNO 204 decrypts the subscriber-related portion of the vSIM credential and checks the accompanying signature. When the decryption has been successfully performed and verified, the vSIM-CORE seals the received vSIM credential on one or more valid platform configurations. The vSIM-CORE then ends the procedure and concludes the installation, at 664.

Alternatively, the MNO 604 could generate the separated key Ks and incorporate an encrypted subscriber-related portion of the vSIM credential in the ticket-i. In this case, the MNO 604 sends only the key Ks to the vSIM-CORE of the target platform, at 662.

FIG. 7 shows an example of a procedure for migrating vSIM credential or its execution environment from a source platform 701 to a target platform 707. The procedure is performed between a source platform 701 including a TSS-DO-S 702, and a TSS-MNO-S 704, and a target platform 707 including TSS-MNO-T 706 and a TSS-DO-T 708. All security-sensitive data including the storage root keys (SRK) are migrated to the target TSS-MNO-T. This requires the same remote owner (RO) on both subsystems TSS-MNO-S and TSS-MNO-T.

The migration procedure of FIG. 7 provides that a complete key hierarchy (1) may be migrated between execution environments of identical stakeholders (2) when and only when for this purpose a specific security policy exists on both platforms and is authorized. The constraints for migration require that only one MNO be involved; however, the credentials can be migrated from one subsystem to another with different owners. The verification that the stakeholders are identical can be performed by the source and destination entities through the attestation mechanism. The configuration transfer can be generalized such that only credentials and policies excluding the software suite are migrated from one platform to another, making the migration independent of functionality.

The procedure begins when TSS-DO-S 702 sends a request for subsystem migration to the TSS-MNO-S 704, at 750. The TSS-MNO-S 704 performs checks on whether the service level of the user and contractual relationship with the target MNO allow the migration at 751. Then the TSS-MNO-S 704 sends a request for subsystem migration (TSS-MNO-S-→TSS-MNO-T) to the TSS-MNO-T 706, at 752. Then the TSS-MNO-T 706 performs a local verification of TSS-MNO-S 704 to ensure that the target platform 707 is in an acceptable state, at 754. The TSS-MNO-T then sends a verification request for performing migration to the TSS-DO-T 708, at 756. The TSS-DO-T 708 performs a confirmation, at 758. Upon successful verification, the TSS-DO-T 708 sends a status message to the TSS-MNO-T 706, at 760. Then the TSS-MNO-T 706 generates a NONCE-MNO-T, at 762. The TSS-MNO-T 706 sends its certificate, the nonce NONCE-MNO-T, current status S_(i,t) and the security policy to TSS-MNO-S 704, at 764. Then the TSS-MNO-S 704 performs a verification of the platform and prepares it for migration at 766. Upon a successful verification, the TSS-MNO-S 704 performs a serialization of the source platform 701, at 768. Serialization is the transformation of an entity into a bit-stream of information and conveyance of it through a communication channel to enable the receiving party to reconstruct the entity to its original form. Then the TSS-MNO-S 704 sends a message containing a serialized entity of the source subsystem TSS-MNO-S to the TSS-MNO-T 706, at 770. The TSS-MNO-T imports the source subsystem, at 772. Then the TSS-MNO-T sends a status message to the TSS-MNO-S 704, at 774. The TSS-MNO.S destroys the TSS-MNO-S, at 776.

While FIG. 7 shows a specific implementation of a migration procedure, the following section describes a more general procedure with a similar end point as the procedure of FIG. 7. For this purpose the device owner starts the migration service of the TSS-MNO-S.

DO_(S)→TSS_(MNO,S):init_migrate_vsim  (Equation 18)

This service provides the following basic functions. The platform MTP-S (or TSS-DM) is assigned by the migration service of the TSS-MNO-S to develop a secure channel (for example TLS and where the communication technology might be Bluetooth, WLAN, USB, etc) to the target platform MTP-T.

After the connection is available, the TSS-MNO-T activates the respective migration service in the TSS-MNO-T to perform the import procedure.

Attestation data of TSS-MNO-S is sent to TSS-MNO-T using the secure channel

TSS_(MNO,S)→TSS_(MNO,D):ATTEST_(TSS) _(MNO,T) (S _(i))  (Equation 19)

The target subsystem TSS-MNO-T then performs a local check of the TSS-MNO-S. If the configuration attestation information, received in 752, is invalid, TSS-MNO-T replies with an error message and terminates the protocol. In the other case, the TSS-MNO-T requests confirmation by the local owner DO.

The target subsystem TSS-MNO-T then generates a random value NONCE-MNO-T. To provide proof of its trustworthiness, the TSS-MNO-T sends all necessary information to the source subsystem TSS-MNO-S. This includes the current status of the S_(i,t), the certificate of TSS-MNO-T, the security policy SP-MNO-T, and the value NONCE-MNO-T.

TSS_(MNO,T)→TSS_(MNO,S):S_(i,T),Cert_(TSS) _(MNO,T) SP_(MNO,T),NONCE_(MNO,T)  (Equation 20)

After the message from the target subsystem is received, the TSS-MNO-S checks the status of TSS-MNO-T. If the target system is in a trusted status and performs an acceptable security policy and configuration, the current status of TSS-MNO-S is linked to the value NONCE-MNO-T and all further actions are halted, thereby deactivating the TSS-MNO-S. It is noted that, where applicable, the source system submits suitable data to reactivate the target system.

The TSS-MNO-S generates a symmetrical migration key K-M, serializes its entity, and encrypts it with the K-M. The K-M is linked to an acceptable configuration of the TSS-MNO-T.

The linked key K-M and the encrypted entity are then sent to the target platform TSS-MNO-T. This includes in particular the completely insulated key hierarchy K-MNO-S together with SRK-MNO-S, the security policy SP-MNO-S, and the required SC-MNO-S. A double nonce is included to preserve freshness and prevent a replay attack. Any return message to the source platform, such as status reporting, requires the nonce NONCE-MNO-S to maintain message freshness.

TSS_(MNO,S)→TSS_(MNO,T):BIND_(TSS) _(MNO,T) (K _(M))  (Equation 21a)

ENC_(K) _(M) (K _(MNO,S),SP_(MNO,S),SC_(MNO,S),NONCE_(MNO,T),NONCE_(MNO,S))  (Equation 21b)

Lastly, the target subsystem TSS-MNO-T decrypts the received K-M and uses SRK-MNO-S as its own SRK. The subsystem checks the received security policy SP-MNO-S and the subsystem configuration SC-MNO-S. With this information the TSS-MNO-T then forms the internal structure of the source subsystem.

After the TSS-MNO-T is successfully completed, the target platform transmits a status report and, where applicable, transmits a platform attestation to the source system.

The source platform TSS-MNO-T deletes all security-sensitive data or renders them permanently unusable. The source system then transmits a status report, if applicable, to the target system and/or performs a platform attestation.

In the migration process of FIG. 7, it is practically assumed that source and target MNO are identical. This restriction can be lifted in other variants of the same protocol, concurrently ruling out the necessity to transfer a serialized entity of the TSS-MNO from source to target. For this, the migration service on the target may receive an authorized migration request from a source TSS-MNO-A-S, with a designated target MNO-B-T, for which a TSS on the target is not necessarily present, In this case the target first invokes a remote take ownership procedure with MNO-B to install a TSS-MNO-B-T. The migration protocol can the run essentially unchanged, but omitting transmission of the serialized entity of TSS-MNO-A-S and instead only transmitting the non-executable parts of that TSS necessary for network access, charging and other desired functions in cooperation with MNO-B, in particular the IMSI of the source vSIM. Regarding IMSI migration, the subscriber may keep the old, unique subscription number MSISDN even when a new IMSI is created and used by the MNO-B.

FIG. 8 shows an example of a communication system configured to perform a first procedure for allowing access of a communication subscriber 802 to a cell based communication network using the software based authorization credentials of the trusted mobile platform 200 of FIG. 2. The approach of FIG. 8 allows access of a communications subscriber 802 to a wireless communications network using software-based access authorization credentials.

The primary objective of the virtual software-based access authorization credential is to ensure a functional substitute for a conventional security token (SIM card) for subscriber authentication in wireless communications networks. In addition to the primary objective of offering a substitute for the conventional SIM function, this procedure links the access authorization credential to a specified trusted platform configuration.

All subscriber-related methods are carried out within the TSS-MNO and by use of the service vSIM-CORE. While algorithms for the GSM standards A3 and A8 are shown below for purposes of example, similar techniques could be used with authentication algorithms of other wireless technologies as well. In the example presented below, these algorithms are responsible for the subscriber authentication and key generation. The algorithm A5/3 for securing the communications channel is integrated within TSS-DM.

Before the procedure of FIG. 8 begins, it is assumed the MTP 200 has performed an initial startup process and loaded the trusted operating system and trusted services. This procedure in particular includes the instantiation of the services vSIM-CORE and vSIM-MGMT. The trustworthiness of the platform is checked so that the installed hardware and running software are in a trusted state and configuration. The MTP is able to report and certify this state when queried by an authorized entity.

The procedure is divided into two phases. Phase 1 constructs the protocol for initializing the services vSIM-CORE and vSIM-MGMT. Subscriber authentication, for example, is performed in Phase 2, taking the GSM standard by way of example into account and using a vSIM credential to carry out the authentication algorithm without changes to the authentication protocol messages, which take place between the MNO and the device.

Phase 1 begins when the local user initializes the vSIM service and performs an authentication. For this purpose the user 802 sends their unambiguous identifier ID-U, together with the correct password CHV-U, to the vSIM-MGMT service, at 850.

The service vSIM-MGMT checks the transmitted user data, and if the check is successful loads the respective identity credential (user-related portion of the vSIM credential) from the protected storage area, at 852. The identity credential contains in particular the signature key of the user U 802.

U→vSIM_(MGMT):ID_(U),CHV_(U)  (Equation 22)

The service vSIM-MGMT then connects to the trusted interface of the service vSIM-CORE and sends an initialization request to vSIM-CORE, at 854. After vSIM-CORE has received this request it generates a random value RAND-AUTH and sends this value as an authentication message to the service vSIM-MGMT, at 856.

vSIM_(CORE)→vSIM_(MGMT):RAND_(AUTH)  (Equation 23)

The service vSIM-MGMT uses the respective private portion of the signature key of the user U, signs the authentication message RAND-AUTH, and sends this value back to the service vSIM-CORE

vSIM_(MGMT) →vSIM_(CORE):SIGN_(U)(RAND_(AUTH))  (Equation 24)

As soon as vSIM-CORE has received the signed message it checks the message status. After a successful check, the service vSIM-CORE decrypts the subscriber-related portion of the vSIM credential and initializes the GSM algorithms A3 and A8 For initialization, vSIM-CORE uses the subscriber data IMSI-i and Ki of the vSIM credential, at 858.

Phase 2 begins, when the vSIM-CORE communicates indirectly (via the TSS-DM) with the MNO. The communication between the involved communication parties occurs transparently. For this purpose the TSS-DM 202 must provide suitable methods or services which relay these messages between the service vSIM-CORE and the MNO 806.

The following protocol sequence represents the vSIM-based authentication method in GSM networks, and is provided only as an example. First the MTP initializes the authentication method, and for this purpose sends the command GSM_AUTH_ALGORITHM to the service vSIM-CORE of the TSS-MNO.

In the next step, the MTP 200 establishes access to the network 806 via the TSS-DM, at 860. Now, subscriber authentication is performed 862 according to the following procedure. For this purpose the TSS-MNO 204 sends the identifier IMSI-i (or TMSI-i) to the MNO.

vSIM_(CORE)→MNO:IMSI_(i)  (Equation 25)

The MNO 806 internally generates a series of authentication triplets. These triplets contain an authentication request RAND-i, a temporary session key Kc, and the expected authentication response SRES. The Kc and the SRES are computed using the GSM A3/A8 algorithm. The MNO 806 replies to the MTP 200 with the authentication request RAND-i.

MNO→vSIM_(CORE):RAND_(i)  (Equation 26)

The RAND-i is relayed by the TSS-DM 202 to the service vSIM-CORE of the TSS-MNO. The vSIM-CORE then uses the A3 algorithm together with the key Ki. The result of the A3 algorithm is the authentication response SRES*.

The vSIM-CORE sends this message SRES* to the MNO.

vSIM_(CORE)→MNO:SRES*  (Equation 27)

Lastly, the MNO compares the SRES to SRES*. If these are identical, the subscriber is considered to be authenticated. The vSIM-CORE and MNO deduce the shared session key Kc and transmit Kc to the TSS-DM. The TSS-DM then accepts Kc for establishing a secure communications channel.

FIGS. 9 and 10 show an example of a communication system configured to perform a second procedure for allowing access of a user to a cell based communication network using remote attestation of the trusted mobile platform 200 of FIG. 2. In FIG. 9, there is a general communication domain 910, and a smaller MNO domain 915 which lies completely within the bounds of the general communications domain 910. The network 918, also includes separate subscription-dependent services 920 which are related to the MNO, subscription-independent services 925, and other services 930 such as location based services and/or wireless local area networks (WLAN).

In comparison to the procedure of FIG. 8, this second procedure uses the technological possibilities of platform attestation for ensuring access to the network in order to use free or optional services that are subscription-independent and/or non-subscriber-related, such as public services.

In addition to the primary objective of offering a substitute for the conventional SIM functions, the second procedure links the access authorization credential to a specified trusted platform configuration, and provides a mutual authentication between the MNO and the MTP. In addition, the second procedure provides core network access to subscription-independent and/or non-subscriber-related services in a general communications domain, fine-grained function limitations such as SIM lock, and dynamic downgrade/upgrade of services.

As shown in FIG. 9, all devices within a generally accessible communications domain are able to use or access subscription-independent and/or non-subscriber-related services (with respect to the MNO) of the core network. Such services may be, for example, location-based services or WLAN-based Internet access. For the case that a mobile telephone is associated with the general communications domain, the mobile telephone uses attestation mechanisms to obtain access to the core network.

The transition to the subscriber-authenticated region (subscription-dependent MNO services) of the MNO requires successful completion of subscriber authentication by use of a vSIM credential. An MTP thus has access to services within the region of the specific communications services offered by the MNO (GSM, UMTS, etc.), as well as access to the services offered by the core network.

FIG. 10 shows an example of the second procedure for allowing access of a communication subscriber to a cell based communication network using remote certification of the MTP 200 of FIG. 2. Before the procedure may begin it is assumed that the MTP 200 has performed an initial startup process and loaded the trusted operating system and trusted services. This procedure in particular includes the instantiation of the services vSIM-CORE and vSIM-MGMT. The trustworthiness of the platform is checked so that the installed hardware and running software are in a trusted state and configuration. The MTP 200 is able to report and certify this state when queried by an authorized entity.

The procedure shown in FIG. 10 is divided into three phases. The first phase of the procedure describes the access to the core network. The procedure uses platform certification and ticketing mechanisms. In the second phase the vSIM credential is initialized. Lastly, the third phase implements the method for subscriber authentication.

Phase 1 begins when the MTP 200 initializes the base authentication of the device. For this purpose the trusted execution environment TSS-DM 202 directs a platform attestation and device authentication to the MNO 1006. The TSS-DM 202 then performs this request and connects to the respective network access point (NAP-MNO 1002), at 1050. For this purpose the TSS-DM 202 generates a random value RAND-BASE and performs a platform attestation. The base authentication service then sends the execution environment TSS-DM 202 the value RAND-BASE, the attestation data, and its certificate Cert-DM to the network access point NAP-MNO.

TE_(DM)→NAP_(MNO):RAND_(BASE),Cert_(TSS) _(DM) ATTEST(S _(i))  (Equation 28)

As soon as this request is received by the NAP-MNO, the NAP-MNO checks the status of the MTP 200. In the event that the integrity check fails or no accepted reference state is found, the NAP-MNO terminates the protocol and replies with an error message. If the certification of the platform is successful, the MTP 200 is considered to be trustworthy.

An accredited entity of the NAP-MNO then generates a network ticket together with a session key K-BASE 1052. Such an entity may be, for example, an authentication center (AUC-MNO) which is a part of the mobile network provider MNO. K-BASE is a minimally used session key which establishes a tunnel between the MTP and the NAP-MNO. This tunnel can be used to protect the distribution of traffic-oriented keys that perform the bulk of the data encryption workload. The selection of this key is made by an authentication trusted third party.

The ticket essentially contains the following information, where REALM identifies the PLMN entity (AuC, VLR, HLR, etc.) involved in the direct communication with the device and LIFETIME a ticket expiration value:

TiCket_(BASE):={ID_(MTP),ID_(NAP),K_(BASE),REALM_(BASE),LIFETIME_(BASE)}  (Equation 29)

The AUC-MNO then encrypts the Ticket-BASE, using the public (or, where applicable, the shared) key K-NAP, and also encrypts K-BASE by binding it to the public key of the K-TSS-DM, and sends both to the NAP-MNO, at 1054. The NAP-MNO relays the information to the client platform, at 1056. The message is also linked to a trusted subsystem TSS-DM 202 together with the respective public key K-TSS-DM and a valid platform configuration. It should be noted that TSS-DM 202 cannot by itself decrypt the Ticket-BASE since the ticket can only be decrypted by using the private K-NAP and the TSS-DM 202 doesn't have it. Rather, TSS-DM 202 forwards the encrypted Ticket-BASE to the NAP-MNO in a later step where the encrypted Ticket-BASE can be decrypted.

$\begin{matrix} {\left. {AUC}_{MNO}\rightarrow{{TSS}_{DM}\text{:}{{BIND}_{K_{{TSS}_{DM}}}\left( K_{BASE} \right)}} \right.,} & \left( {{Equation}\mspace{14mu} 30a} \right) \\ {{{ENC}_{K_{NAP}}\left( {Ticket}_{BASE} \right)},} & \left( {{Equation}\mspace{14mu} 30b} \right) \\ {{SIGN}_{{AUC}_{MNO}}\left( {RAND}_{BASE} \right)} & \left( {{Equation}\mspace{14mu} 30c} \right) \end{matrix}$

As soon as the TSS-DM 202 has received the signed message, it checks the status of the signed value RAND-BASE, at 1058. If the information is invalid or is rejected, the subsystem replies with an error message and terminates the protocol. In another case, the AUC-MNO is certified by the authentication response.

The TSS-DM 202 then decrypts the session key K-BASE and sends the encrypted Ticket-BASE together with an authenticator A-MTP to the NAP-MNO. In the present case the authenticator A-MTP is composed of the platform identity ID-MTP, the current network address ADDR, and a time stamp TIME.

TSS_(DM)→NAP_(MNO):ENC_(K) _(NAP) (Ticket_(BASE)),A_(MTP)  (Equation 31)

The ticket base Ticket-BASE is simply passed by TSS_(DM) to the network where it is decrypted. When the NAP-MNO has received the encrypted ticket, it verifies the embedded information. With the encryption of Ticket-BASE using the public part of K-NAP an effective binding takes place. In particular, K-BASE, as part of the ticket is bound to the NAP. If the status is valid, the platform is certified and access to the general services is granted. The limited use session key K-BASE is now bound to both the MTP 200 and the NAP-MNO to setup the secure tunnel between the two entities.

The procedure of Phase 2 is similar to 850-858 of in the procedure of FIG. 8.

There are two options for completing phase three, the first option performs subscriber authentication with compatibility to the GSM standard, by way of example. In an additional step the key K-BASE is replaced by the session key Kc on the side of the NAP-MNO and of the MTP, at 1070.

At this point, a mutual authentication is performed between the AUC-MNO and U. The AUC-MNO is certified by a signed authentication request, at 1056. On the other side, the user 1008 verifies his identity by means of SRES. The authentication between the NAP-MNO and U 1008 is implicitly verified by a valid message key Kc.

This method may be optimized by embedding RAND-i beforehand in the encrypted key message, at 1056. In this case, vSIM-CORE extracts the RAND-i from this message, computes the authentication response SRES, and sends both results to the MNO. The MNO internally generates the expected SRES and the corresponding session key Kc.

Additional steps must be performed when an explicit authentication of these entities is required. The NAP is certified with respect to the platform by means of the following procedure. First, the NAP removes the time stamp from the authenticator Au. The NAP then increases the value and encrypts it, using the shared session key Kc (or a key derived from same). Lastly, the NAP sends the message back to MTP.

In the second option for phase 3 (not pictured), the authentication methods may deviate from the GSM authentication standard. This variant presents a slightly modified authentication method which, however, provides a significant increase in security for the PLMN. In particular, protocol errors in signal system 7 (SS7) may be avoided in this manner.

The following variant makes use of the former negotiated information for the core network access from phase 1. In conventional GSM infrastructures an authentication triplet is sent over the SS7 network. This triplet contains a challenge RAND, the correct response SRES, and the message key Kc.

Although the initial access to the mobile communications network is established by the message key K-BASE, renewal of this key is not necessary. This applies in particular to embedding of the session key Kc. Transmission of unprotected session keys is thereby avoided.

The basic purpose of this option is to make use of the existing communications tunnel between the NAP-MNO and the MTP which is protected on the basis of the key K-BASE. Instead of renewing the session key, the MNO sends only a service update message to the respective network access point NAP and MTP.

In current PLMN, the address space for network subscribers, for example represented by IMSI numbers in the GSM or UMTS systems, is prone to shortages. The network access method based on tickets is a way to overcome this problem. To this end, the IMSI information (or similar network subscriber ID) can be used together with the MTP identity delivered by the TSS-DM to the NAP-MNO, or with any other identity-bearing information that TSS-DM can obtain and forward to the NAP-MNO. After the above protocol has succeeded and the requesting MTP has gained network access, the NAP-MNO is then actively involved in service requests emanating from the device or directed to it, in order to correctly map communication with the same IMSI to the current ADDR data and thereby to the correct entity. Note again that ADDR data, in the context of GSM or UMTS systems, would be IMSI or TMSI. That is, the NAP-MNO extends the existing identification methods of PLMN base stations.

This method can be used to establish in particular a group IMSI addressing for instance in the case of machine-to-machine communication, or for device fleets belonging to a single stakeholder.

Furthermore, more than one network access tickets for the same device may be valid at the same time, for different service levels or tariffs, signified also by additional information in Ticket-BASE. Those additional identity-information may also be used to identify different vSIM entities and/or users sharing the same IMSI on the same or different MTPs.

Tickets may also be augmented by information on the validity period information determining for instance a period of accessibility for a certain service, or a particular tariff during such a period of time. The NAP or another entity then obtains the task to decide on and enforce decisions on such time-limited services based on the ticket identity and the known validity period associated to it.

FIG. 11 shows a third procedure for subscriber authentication for a general network infrastructure. For the procedure of FIG. 11, the structural design of the subscriber-related portion of the vSIM credential and the functionality or integrated algorithms of the trusted service vSIM-CORE must adhere to certain requirements.

The vSIM credential of FIG. 11 is an access authorization credential based on the identity of a subject. This access authorization credential, not bound to the 2G/3G structural mold, is a generalization of its counterparts in FIGS. 8 and 10 and is used to certify the identity of a communications subscriber. The vSIM credential contains a unique identifier ID-U of the subject U 1110 and at least one information item based on cryptographic encryption mechanisms (for example, symmetrical or asymmetrical keys) or non-cryptographic encryption mechanisms (for example, one-way hash chain). Only authorized subjects are able to generate or read a vSIM credential or modify the contained information. A vSIM credential may contain additional information such as the device identity or a list of valid application areas.

The MTP 1108 instantiates a vSIM-CORE service which runs in a separate, protected execution environment. The service vSIM-CORE is responsible for the core functioning of the subscriber authentication. In particular, this service performs the actual authentication mechanisms. The specific design of mechanisms or procedures depends on the particular application. The service vSIM-CORE may import a trusted functionality, possibly based on the particular use-case, and may also provide other (external) trusted services. vSIM-CORE also contains at least one subscriber-related portion of a vSIM credential.

Before the procedure of FIG. 11 begins, the MTP 1108 has performed an initial startup process and loaded the trusted operating system and trusted services. These contain in particular the instantiation of the services vSIM-CORE and vSIM-MGMT. The trustworthiness of the platform is checked so that the installed hardware and running software are in a trusted state and configuration. The MTP is able to report and certify this state when queried by an authorized entity.

The procedure of FIG. 11 is divided into three phases. Phase one 1120 is remote certification. Phase two 1130 is the initialization of the vSIM credential. Phase three 1140 is the subscriber authentication procedure.

In phase one 1120, platform certification is used to perform a device-authentication, as described by way of example above. In this general case provided in FIG. 11, the network entity MNO 1112 is replaced by a respective entity of the general network infrastructure. Such an entity may be, for example, an authentication server (ALS) within this network, where the server is not necessarily tied to 2G or 3G technology but could apply to future networks such as long term evolution (LTE).

Phase two 1130, the initialization of the vSIM services and of the vSIM credential is performed in a similar manner as the phase two procedure of FIG. 10. However, the procedure is based on generalized assumptions, thus enabling a broader basis for further authentication methods and protocols.

Phase three 1140 is the subscriber authentication procedure for authenticating and authorizing a given subscriber for services offered by the ALS. In contrast, the procedures of FIGS. 8 and 10 are limited to procedure for subscriber authentication of shared secret information (symmetrical key Ki as per GSM). In particular, this limitation is not present in the generic procedure of FIG. 11. Thus, in the procedure of FIG. 11, no shared secret is employed and the authentication process is entirely based on certificate based asymmetric cryptography. For example, using Diffie-Hellman with a certificate authority (CA), a key exchange can take place between trusted entities. In such a scenario the parties require mutual identity with verification by the CA.

In phase three 1140, a random value RAND-SRV is used to request an expansion of services on the ALS. The TE-MNO extracts the RAND-SRV from the ticket-BASE. The TSS-MNO then produces the authentication response XRES*-SRV and signs the RAND-SRV with its private signature key K-priv-TM-AS. Together with UID and a service identifier SRV this signature XRES*-SRV is sent to the ALS As soon as the ALS has received this message, it verifies the signature of the XRES*-SRV. If the signature is valid, the platform is certified and a service expansion is performed.

Although features and elements are described above in particular combinations, each feature or element can be used alone without the other features and elements or in various combinations with or without other features and elements. The methods or flow charts provided herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable storage medium for execution by a general purpose computer or a processor. Examples of computer-readable storage mediums include a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs).

Suitable processors include, by way of example, a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), and/or a state machine.

A processor in association with software may be used to implement a radio frequency transceiver for use in a wireless transmit receive unit (WTRU), user equipment (UE), terminal, base station, radio network controller (RNC), or any host computer. The WTRU may be used in conjunction with modules, implemented in hardware and/or software, such as a camera, a video camera module, a videophone, a speakerphone, a vibration device, a speaker, a microphone, a television transceiver, a hands free headset, a keyboard, a Bluetooth® module, a frequency modulated (FM) radio unit, a liquid crystal display (LCD) display unit, an organic light-emitting diode (OLED) display unit, a digital music player, a media player, a video game player module, an Internet browser, and/or any wireless local area network (WLAN) or Ultra Wide Band (UWB) module. 

1. A method of registering and receiving a virtual subscriber identity module (vSIM) credential, on a mobile trusted processor (MTP) having a vSIM-core trusted execution environment, and a vSIM-management (vSIM-MGMT) trusted execution environment, the method comprising: sending a request for registration and ticket to a trusted point of sale (POS); receiving a ticket from the trusted POS in response to the request, and other trust verification procedures.
 2. The method of claim 1 further comprising: establishing a trusted relationship with the POS.
 3. The method of claim 2 wherein the establishing a trusted relationship includes performing an attestation procedure with the POS.
 4. The method of claim 2 wherein the establishing a trusted relationship includes performing an authentication procedure with the POS.
 5. A method executed by a remote point of sale (POS) for registering and providing a virtual subscriber identity module (vSIM) credential to a mobile trusted processor (MTP) having a vSIM-core trusted execution environment, and a vSIM-management (vSIM-MGMT) trusted execution environment, the method comprising: receiving a request for registration and ticket from the MTP; selecting the a registration ticket; sending subscriber registration data relating to the MTP and a request for a registration ticket to a network provider (MNO); receiving a registration ticket from the MNO; and sending the registration ticket to the MTP.
 6. The method of claim 5 wherein the POS is a trusted POS.
 7. The method of claim 5 wherein sending subscriber registration data relating to the MTP and a request for a registration ticket includes attestation data.
 8. The method of claim 5 further comprising establishing a trusted relationship with the MNO.
 9. The method of claim 5 further comprising establishing a trusted relationship with the MTP.
 10. The method of claim 5 wherein the received ticket request includes at least part of a public encryption key.
 11. The method of claim 5 wherein subscriber registration data relating to the MTP and a request for a registration ticket includes a signature for authentication.
 12. The method of claim 5 wherein registration ticket includes attestation information.
 13. The method of claim 5 wherein registration ticket includes authentication information.
 14. The method of claim 5 wherein registration ticket includes a signed certificate.
 15. The method of claim 5 further comprising: establishing a certified asymmetric key pair with the MTP.
 16. The method of claim 5 wherein the received registration ticket is encrypted.
 17. The method of claim 5 wherein the POS is not trusted.
 18. A mobile trusted platform (MTP) comprising: a device manufacturer-trusted subsystem (TSS-DM) configured to store and provide credentials related to a manufacture of the MTP; a mobile network operator-trusted subsystem (TSS-MNO) configured to store and provide credentials related to a mobile network operator (MNO); a device user-trusted subsystem (TSS-U) configured to store and provide credentials related to user of the MTP.
 19. The MTP of claim 18 wherein the TSS-MNO includes a virtual subscriber identity module (vSIM) core services unit, configured to store, provide and process credential information relating to the MNO.
 20. The MTP of claim 18 wherein TSS-DO includes a virtual subscriber identity module (vSIM) management unit, configured to store, provide and process credential information relating to the user of the MTP.
 21. The MTP of claim 18 wherein TSS-DO and the TSS-MNO communicate through a trusted virtual subscriber identity module (vSIM) service.
 22. The MTP of claim 1 further comprising: a second TSS-U configured to store and provide credentials relating to a second user of the MTP.
 23. The MTP of claim 18 further comprising: a device owner-trusted subsystem TSS-DO configured to store and provide credentials related an owner of the MTP.
 24. The MTP of claim 18 further comprising: a second TSS-MNO configured to store and provide credentials related to a second MNO. 